| 翻訳と辞書 |
| Service Normalization Pattern ： ウィキペディア英語版 |
Service Normalization Pattern
Service Normalization is a design pattern, applied within the service-orientation design paradigm, whose application ensures that services〔(Services )〕 that are part of the same service inventory〔(service inventory )〕 do not contain any redundant functionality.〔Kanu Tripathi.(Service Transaction Handling Without WS-AtomicTransaction )().Date accessed: 25 April 2010.〕 This design pattern emphasizes on creating normalized services, much like creating normalized tables in a database where all the attributes in a table only relate to the entity described by the table and any attributes that do not directly relate to the entity are either put into a new table or in an existing table that better fits the context of that attribute.
==Rationale==
When different teams are delivering multiple services as part of automating various business processes, there is a possibility that some of these services might end up having duplicate functionality. For example, the automation of two different business processes, by two different teams, which need to exchange messages with the same legacy system may end up in two different versions of a wrapper service that are created to enable exchange of messages with the services. This overlap in functionality can lead to other problems including which service to be advertised as the official service for the provision of a particular functionality and maintenance of redundant services as they can easily get out of alignment.
In order to deliver services, as part of the same service inventory, that are free of any duplicate functionality, the functional boundary of each service needs to be carefully established so that it is not in conflict with any other service. The Service Normalization〔Thomas Erl, Herbjörn Wilhelmsen.(Service Normalization design pattern )(). Date accessed: 6 April 2010.〕 design pattern provides guidelines for creating service inventories that contain streamlined services without any functional duplication.〔Thomas Erl.(Introducing SOA Design Pattern )(). Date accessed: 6 April 2010.〕 By creating normalized services, the purpose of the service also becomes clearer to its potential consumers.〔Yefim V. Natis, Massimo Pezzini.(Twelve Common SOA Mistakes and How to Avoid Them )().Date accessed: 25 April 2010.〕
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Service Normalization Pattern」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|